Skip to content

chore: apply npm pkg fix to silence publish warnings - #13

Merged
facundofarias merged 1 commit into
mainfrom
chore/npm-pkg-fix
Oct 3, 2026
Merged

facundofarias merged 1 commit into
mainfrom
chore/npm-pkg-fix

Conversation

@facundofarias

Copy link
Copy Markdown
Member

Every npm publish warned that it had auto-corrected package.json. This commits the normalized values (output of npm pkg fix):

  • bin.pixelvault: ./bin/pixelvault.mjs → bin/pixelvault.mjs
  • repository.url: → git+https://github.com/pixelvault-dev/cli.git

No behavior change. npm already published these exact values, so this only makes the repo match the published package. npm publish --dry-run now prints no warnings, and node bin/pixelvault.mjs --help still works after a build. No version bump needed; the fix goes out with the next release.

🤖 Generated with Claude Code

npm publish auto-corrected the bin path and repository.url on every
release. Commit the normalized forms so the published package.json
matches the repo and the warning goes away.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@facundofarias
facundofarias merged commit fa2ff14 into main Oct 3, 2026
2 checks passed
@facundofarias
facundofarias deleted the chore/npm-pkg-fix branch October 3, 2026 20:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant